home *** CD-ROM | disk | FTP | other *** search
iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) NNNNAAAAMMMMEEEE _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp - compare or print out _t_e_r_m_i_n_f_o descriptions SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp [_----_dddd] [_----_cccc] [_----_nnnn] [_----_IIII] [_----_LLLL] [_----_CCCC] [_----_rrrr] [_----_uuuu] [_----_ssss _dddd| _iiii| _llll| _cccc] [_----_vvvv] [_----_VVVV] [_----_1111] [_----_wwww _w_i_d_t_h] [_----_AAAA _d_i_r_e_c_t_o_r_y] [_----_BBBB _d_i_r_e_c_t_o_r_y] [_t_e_r_m_n_a_m_e . . .] DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp can be used to compare a binary _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo entry with other terminfo entries, rewrite a _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo description to take advantage of the _uuuu_ssss_eeee_==== terminfo field, or print out a _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo description from the binary file (_tttt_eeee_rrrr_mmmm) in a variety of formats. In all cases, the boolean fields will be printed first, followed by the numeric fields, followed by the string fields. DDDDeeeeffffaaaauuuulllltttt OOOOppppttttiiiioooonnnnssss If no options are specified and zero or one _t_e_r_m_n_a_m_e_s are specified, the _----_IIII option will be assumed. If more than one _t_e_r_m_n_a_m_e is specified, the _----_dddd option will be assumed. CCCCoooommmmppppaaaarrrriiiissssoooonnnn OOOOppppttttiiiioooonnnnssss [[[[----dddd]]]] [[[[----cccc]]]] [[[[----nnnn]]]] _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp compares the _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo description of the first terminal _t_e_r_m_n_a_m_e with each of the descriptions given by the entries for the other terminal's _t_e_r_m_n_a_m_e_s. If a capability is defined for only one of the terminals, the value returned will depend on the type of the capability: _FFFF for boolean variables, _----_1111 for integer variables, and _NNNN_UUUU_LLLL_LLLL for string variables. _----_dddd produces a list of each capability that is different between two entries. This option is useful to show the difference between two entries, created by different people, for the same or similar terminals. _----_cccc produces a list of each capability that is common between two entries. Capabilities that are not set are ignored. This option can be used as a quick check to see if the _----_uuuu option is worth using. _----_nnnn produces a list of each capability that is in neither entry. If no _t_e_r_m_n_a_m_e_s are given, the environment variable _TTTT_EEEE_RRRR_MMMM will be used for both of the _t_e_r_m_n_a_m_e_s. This can be used as a quick check to see if anything was left out of a description. SSSSoooouuuurrrrcccceeee LLLLiiiissssttttiiiinnnngggg OOOOppppttttiiiioooonnnnssss [[[[----IIII]]]] [[[[----LLLL]]]] [[[[----CCCC]]]] [[[[----rrrr]]]] The _----_IIII, _----_LLLL, and _----_CCCC options will produce a source listing for each terminal named. _----_IIII use the _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo names _----_LLLL use the long C variable name listed in <_tttt_eeee_rrrr_mmmm_...._hhhh> _----_CCCC use the _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp names _----_rrrr when using _----_CCCC, put out all capabilities in _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp form PPPPaaaaggggeeee 1111 iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) If no _t_e_r_m_n_a_m_e_s are given, the environment variable _TTTT_EEEE_RRRR_MMMM will be used for the terminal name. The source produced by the _----_CCCC option may be used directly as a _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp entry, but not all of the parameterized strings may be changed to the _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp format. _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp will attempt to convert most of the parameterized information, but anything not converted will be plainly marked in the output and commented out. These should be edited by hand. All padding information for strings will be collected together and placed at the beginning of the string where _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp expects it. Mandatory padding (padding information with a trailing '/') will become optional. All _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp variables no longer supported by _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo, but which are derivable from other _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo variables, will be output. Not all _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo capabilities will be translated; only those variables which were part of _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp will normally be output. Specifying the _----_rrrr option will take off this restriction, allowing all capabilities to be output in _t_e_r_m_c_a_p form. Note that because padding is collected to the beginning of the capability, not all capabilities are output. Mandatory padding is not supported. Because _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp strings are not as flexible, it is not always possible to convert a _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo string capability into an equivalent _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp format. A subsequent conversion of the _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp file back into _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo format will not necessarily reproduce the original _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo source. Some common _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo parameter sequences, their _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp equivalents, and some terminal types which commonly have such sequences, are: _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp Representative Terminals _%%%%_pppp_1111_%%%%_cccc _%%%%_.... adm _%%%%_pppp_1111_%%%%_dddd _%%%%_dddd hp, ANSI standard, vt100 _%%%%_pppp_1111_%%%%_''''_xxxx_''''_%%%%_++++_%%%%_cccc _%%%%_++++_xxxx concept _%%%%_iiii _%%%%_iiii ANSI standard, vt100 _%%%%_pppp_1111_%%%%_????_%%%%_''''_xxxx_''''_%%%%_>>>>_%%%%_tttt_%%%%_pppp_1111_%%%%_''''_yyyy_''''_%%%%_++++_%%%%_;;;; _%%%%_>>>>_xxxx_yyyy concept _%%%%_pppp_2222 is printed before _%%%%_pppp_1111 _%%%%_rrrr hp UUUUsssseeee==== OOOOppppttttiiiioooonnnn [[[[----uuuu]]]] _----_uuuu produces a _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo source description of the first terminal _t_e_r_m_n_a_m_e which is relative to the sum of the descriptions given by the entries for the other terminals _t_e_r_m_n_a_m_e_s. It does this by analyzing the differences between the first _t_e_r_m_n_a_m_e and the other _t_e_r_m_n_a_m_e_s and producing a description with _uuuu_ssss_eeee_==== fields for the other terminals. In this manner, it is possible to retrofit generic terminfo entries into a terminal's description. Or, if two similar terminals exist, but were coded at different times or by different people so that each description is a full description, using _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp will show what can be done to change one description to be relative to the other. PPPPaaaaggggeeee 2222 iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) A capability will get printed with an at-sign (@) if it no longer exists in the first _t_e_r_m_n_a_m_e, but one of the other _t_e_r_m_n_a_m_e entries contains a value for it. A capability's value gets printed if the value in the first _t_e_r_m_n_a_m_e is not found in any of the other _t_e_r_m_n_a_m_e entries, or if the first of the other _t_e_r_m_n_a_m_e entries that has this capability gives a different value for the capability than that in the first _t_e_r_m_n_a_m_e. The order of the other _t_e_r_m_n_a_m_e entries is significant. Since the terminfo compiler _tttt_iiii_cccc does a left-to-right scan of the capabilities, specifying two _uuuu_ssss_eeee_==== entries that contain differing entries for the same capabilities will produce different results depending on the order that the entries are given in. _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp will flag any such inconsistencies between the other _t_e_r_m_n_a_m_e entries as they are found. Alternatively, specifying a capability _a_f_t_e_r a _uuuu_ssss_eeee_==== entry that contains that capability will cause the second specification to be ignored. Using _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp to recreate a description can be a useful check to make sure that everything was specified correctly in the original source description. Another error that does not cause incorrect compiled files, but will slow down the compilation time, is specifying extra _uuuu_ssss_eeee_==== fields that are superfluous. _iiii_nnnn_ffff_oooo_cccc_mmmm_pppp will flag any other _t_e_r_m_n_a_m_e _uuuu_ssss_eeee_==== fields that were not needed. OOOOtttthhhheeeerrrr OOOOppppttttiiiioooonnnnssss [[[[----ssss dddd||||iiii||||llll||||cccc]]]] [[[[----vvvv]]]] [[[[----VVVV]]]] [[[[----1111]]]] [[[[----wwww _w_i_d_t_h]]]] _----_ssss sorts the fields within each type according to the argument below: _dddd leave fields in the order that they are stored in the _t_e_r_m_i_n_f_o database. _iiii sort by _t_e_r_m_i_n_f_o name. _llll sort by the long C variable name. _cccc sort by the _t_e_r_m_c_a_p name. If the _----_ssss option is not given, the fields printed out will be sorted alphabetically by the _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo name within each type, except in the case of the _----_CCCC or the _----_LLLL options, which cause the sorting to be done by the _tttt_eeee_rrrr_mmmm_cccc_aaaa_pppp name or the long C variable name, respectively. _----_vvvv prints out tracing information on standard error as the program runs. _----_VVVV prints out the version of the program in use on standard error and exit. PPPPaaaaggggeeee 3333 iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) iiiinnnnffffooooccccmmmmpppp((((1111MMMM)))) _----_1111 causes the fields to be printed out one to a line. Otherwise, the fields will be printed several to a line to a maximum width of 60 characters. _----_wwww changes the output to _w_i_d_t_h characters. CCCChhhhaaaannnnggggiiiinnnngggg DDDDaaaattttaaaabbbbaaaasssseeeessss [[[[----AAAA _d_i_r_e_c_t_o_r_y]]]] [[[[----BBBB _d_i_r_e_c_t_o_r_y]]]] The location of the compiled _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo database is taken from the environment variable _TTTT_EEEE_RRRR_MMMM_IIII_NNNN_FFFF_OOOO . If the variable is not defined, or the terminal is not found in that location, the system _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo database, usually in _////_uuuu_ssss_rrrr_////_ssss_hhhh_aaaa_rrrr_eeee_////_llll_iiii_bbbb_////_tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo, will be used. The options _----_AAAA and _----_BBBB may be used to override this location. The _----_AAAA option will set _TTTT_EEEE_RRRR_MMMM_IIII_NNNN_FFFF_OOOO for the first _t_e_r_m_n_a_m_e and the _----_BBBB option will set _TTTT_EEEE_RRRR_MMMM_IIII_NNNN_FFFF_OOOO for the other _t_e_r_m_n_a_m_e_s. With this, it is possible to compare descriptions for a terminal with the same name located in two different databases. This is useful for comparing descriptions for the same terminal created by different people. FFFFIIIILLLLEEEESSSS _////_uuuu_ssss_rrrr_////_ssss_hhhh_aaaa_rrrr_eeee_////_llll_iiii_bbbb_////_tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo_////_????_////_**** Compiled terminal description database. SSSSEEEEEEEE AAAALLLLSSSSOOOO _cccc_uuuu_rrrr_ssss_eeee_ssss(3X), _cccc_aaaa_pppp_tttt_oooo_iiii_nnnn_ffff_oooo(1M), _tttt_eeee_rrrr_mmmm_iiii_nnnn_ffff_oooo(4), _tttt_iiii_cccc(1M) PPPPaaaaggggeeee 4444 
